In This Topic

.NET Framework, COM, and Excel Development

If you are developing under .NET Framework or COM development platform, and also for Excel development with the Excel Option, (at least) one of the following .NET runtimes must be installed on your development and production computers:

.NET Framework 4.7.2
.NET Framework 4.8
.NET Framework 4.8.1

Note that

.NET Framework 4.7.2 is included with Windows 10 version 1803 (April 2018 Update), version 1809 (October 2018 Update), Windows Server versions 1803 and 1809, and Windows Server 2019.
.NET Framework 4.8 is included with Windows 10 version 1903 (May 2019 Update) and later.

.NET 6+ Development

If you are developing under .NET 6+ development platform, (at least) one of the following .NET runtimes must be installed on your development computer:

.NET 6 or 7

In runtime, all user interface features (such as controls, dialogs, and live binding; Windows Forms and WPF) and nonvisual components are supported both under .NET Framework and .NET 6+. However, "designing" them (this includes tasks like dragging from the Toolbox, or configuring in Properties window) in Visual Studio is only possible in .NET Framework projects. In order to achieve visual design for .NET 6+ projects, the developer can make two project files over the same set of source files, one targeting .NET Framework and one targeting .NET 6+, and use the project that targets .NET Framework for visual design tasks.

On the production computers, you can either use framework-dependent deployment (FDD), and in such case one of the above runtimes must be installed on the production computer, or you can use a self-contained deplyment (SCD), in which case the .NET runtime you have selected does not have to be preinstalled on the production computer (but it is deployed along with your application). See .NET application publishing overview for more information.

.NET

On Linux, you may find Install .NET on Linux page useful, in order to check the supported Linux distributions/versions, and what other dependencies exist. Related to this, you may also want to review:

Overview of how .NET is versioned article
.NET Supported OS Policy article
Microsoft Support for .NET article

If you want to verify the version of .NET on your computer, use the dotnet --info command in the command prompt, and look for the Version field under ".NET runtimes installed:" in the generated output. Do not use dotnet --version, because this command only returns the version of the .NET command-line tools.

Other Runtimes

Other .NET runtimes that are not listed here (Mono, Xamarin, UWP, .NET Framework) are not supported. It is possible that QuickOPC will work on such .NET runtimes as well, but if you decide to use them, you are on your own... QuickOPC may support them in the future.

Python Development

Python programs developer with QuickOPC can run either on .NET Framework, or on .NET 6+. Unless instructed otherwise, QuickOPC chooses the .NET runtime (from the .NET runtimes available on the target computer) automatically. Refer to the paragraphs above for the requirements associated with specific .NET runtimes.

Remarks

For a (incomplete) list of .NET Runtimes QuickOPC has been tested with, consult Knowledge Base article QuickOPC Compatibility Test List.

The features discussed here, or some of them, may not be available in all editions of the product. Check the Product Editions page for differences between the editions. The trial license has all features enabled (and is limited in period for which it provides valid data), but licenses for specific commercial editions may have functionality limitations.

'Support' means that QuickOPC is designed to work and tested on the environment, and vendor's technical support may be contacted for assistance with QuickOPC on the environment. Support may be not available for operating systems, .NET runtimes and other dependencies that are past their active lifecycle at the time of support request, even if they were supported at the time of product release.